Abilities MCP · The Bridge · Wicked Evolutions

Abilities MCP / 01 — In one breath

What it is. Why it exists. How it works. What it brings you.

A translation, before any technical detail. The shape of this product in plain operator language — so the spec that follows lands as confirmation, not first contact.

What

A small program that runs on your computer.

It speaks the Model Context Protocol on one side and HTTPS on the other. Your AI client talks to it locally. It talks to your WordPress sites over the wire.

Why

So one AI conversation reaches every site you operate.

Without it, every site is its own connection, its own paste of credentials, its own mental tax. With it, all of them are one.

How

It registers each site once, holds the keys in your OS keychain, and routes calls.

Your AI asks for a site by handle. The bridge resolves it, attaches the right scoped key, and forwards the call. You see the answer. The keys never leave your machine.

What it brings

One conversation across your whole WordPress fleet.

Stop juggling tabs. Stop re-pasting tokens. Operate every site you run from the same chat — without giving any third party a copy of your data.

Abilities MCP / 02 — Routing

One MCP. Every site you operate.

From your AI client's point of view it looks like one connection. From your point of view it looks like one chat. Underneath, the bridge is doing the routing — picking the right site, attaching the right key, returning the right answer.

Your AI client

Claude · Cursor · Codex

one MCP connection

↔ local stdio / SSE ↔

Bridge · runs on your machine

Abilities MCP

resolves site handles
attaches scoped keys
signs the request

↔ HTTPS · per-site ↔

Site

studio.example

scoped key · admin

Site

shop.example

scoped key · editor

Multisite

network.example

subsites included

The fleet stays separate where it matters — keys, scopes, audit trails are per-site. The conversation stays unified where it matters — you. One person, one chat, one mental model across the whole portfolio.

Abilities MCP / 03 — Transports

SSH for developers. HTTP for everyone.

Two ways to reach the site. The bridge picks based on how the site is set up. Same outcome, different path — chosen so the install never asks an operator to touch infrastructure they don't own.

Path A · HTTPS

For everyone.

A normal HTTPS call to your WordPress site, signed with the scoped key.

If your WordPress is reachable on the open web — which is almost all of them — the bridge talks to it the same way your browser does. Nothing to install on the server. No port to open. No SSH key to manage.

For solopreneurs · operators · anyone with a normal hosted WordPress

Path B · SSH tunnel

For developers.

When the site is behind a firewall or only reachable from your laptop.

Local dev, staging boxes inside a private network, or production behind a VPN — the bridge tunnels through the SSH connection you already use, no public endpoint required. The same chat reaches sites no one else can see.

For developers · agencies · anyone with environments behind a wall

Abilities MCP / 04 — Local tools

Three tools that never touch WordPress.

Most of what the bridge offers is your WordPress, made callable. But three tools live entirely on your machine — they exist so the AI can manage the connection itself, without ever asking you to leave the chat.

site_register

Add a site to the fleet.

Hand the AI a URL and a one-time setup token. It registers the site, stores the scoped key in your OS keychain, and the next message can already work with it.

site_list

See what's connected.

A list of every site this bridge knows about — handles, scopes, last-seen. The AI uses it to disambiguate when you say "the shop site." You use it to audit your own fleet.

site_remove

Cut the connection.

Drop the key from the keychain. The AI loses access immediately. The site itself is unchanged — only this bridge is forgetting it.

Everything else the AI can call is on your WordPress. The bridge is intentionally thin.

Abilities MCP / 05 — How it relates

The bridge is one of three. All three are needed.

Abilities MCP makes the connection. The MCP Adapter on each WordPress site receives it — and Abilities for AI is what's actually being called. None of the three works alone. Installed together, they are the operating layer.

This page

Abilities MCP

The bridge that runs on your machine. Routes one conversation across your fleet.

Layer 02 →

MCP Adapter

The plugin on each site that opens the gate — with consent, scopes, and redaction.

Layer 03 →

Abilities for AI

Every WordPress surface, registered as a callable named operation.